Ai Answer Copier

Created By
XJTLU Media2 months ago
A Model Context Protocol (MCP) server that gives your AI assistant the power to convert Markdown into 14 professional document formats — PDF, DOCX, HTML, LaTeX, CSV, JSON, XML, XLSX, RTF, PNG, and more. Stop copy-pasting. Let the AI do the exporting.
Overview

Why AI Answer Copier? You asked an AI to generate 20 exam questions. It delivered — beautifully. But then reality hits:

Pain Point Manual Workflow With AI Answer Copier Extracting Q&A 10–15 min copying each line 2 seconds (auto-detect) Formatting Math 20 min fixing broken symbols Instant (KaTeX support) LMS Upload 15 min manual CSV entry 1-click export Total Prep Time ~45–60 minutes < 1 minute The last mile of AI workflows is broken. Generating content takes seconds; formatting it for the real world takes an hour. This MCP server eliminates that gap entirely.

14 Export Tools at Your AI's Fingertips Tool Output Format Use Case harmonize_markdown Clean .md Standardize messy AI output convert_to_txt Plain .txt Strip all formatting convert_to_html .html Web pages, email templates convert_to_pdf .pdf Print-ready exams, handouts convert_to_docx .docx Microsoft Word documents convert_to_latex .tex Academic papers, journals convert_to_rtf .rtf Rich text for legacy systems convert_to_csv .csv Kahoot, Quizizz, Google Forms convert_to_json .json APIs, Canvas LMS, custom apps convert_to_xml .xml Moodle, Blackboard, SCORM convert_to_xlsx .xlsx Excel spreadsheets convert_to_image .png Social media, presentations convert_to_md .md Documentation, GitHub generate_html Full HTML doc Self-contained pages with inline styles Every tool accepts a markdown string input and an optional output_path to save directly to disk. Binary formats (PDF, DOCX, XLSX, PNG) intelligently guide the AI to save files rather than dumping raw base64.

Server Config

{
  "mcpServers": {
    "ai-answer-copier": {
      "command": "npx",
      "args": [
        "-y",
        "@xjtlumedia/markdown-mcp-server"
      ]
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
XJTLU Media
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

9 hours ago
Alloy

2 days ago